BayDAG Contribution #8: Landuse and Reindex available in location choice #774
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dhensle
force-pushed
the
BayDAG_cont8_lu_and_reindex_in_loc_choice
branch
from
e6beac9 to
4201d36
Compare
i-am-sijia
approved these changes
Mar 19, 2024
This was referenced May 1, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds the ability to call the landuse table and the "reindex" function in the location choice model. This is required for the SANDAG ABM3 model calibration. Getting county-to-county (or whatever geographic level) flows is important for calibration of workplace location models. The easiest way to accomplish this is to look at the origin home county and the destination county of the alternative and add/subtract utility for the correct combination. The county of the alternative is provided by "reindexing" the county of that zone from the landuse table.
Previous models have gotten around this limitation by creating a separate skim that contains the county. The skim is then called in the model. This requires additional overhead in terms of creating, loading, and maintaining that skim, is not efficient from a memory perspective, and is opaque to the users. This PR aims to provide a better way.
Required for SANDAG ABM3 production? -- yes